-
-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor COM Registration Fixing Tool part 2: remove bugs, return Windows errors, improve UX #12355
Conversation
What is the status of this pr now that pr #12560 has been merged? Has this one been replaced, or is there extra work in this pr? |
@michaelDCurran, to answer your old question: There is extra work in this PR.
#12560 did the back-end. This one does the front-end (UX), and picks up errors
that are not currently being handled or shown to the user.
However I have been unavailable for several months, and this has fallen enough
behind master that it can no longer merge/rebase as-is.
I am working to bring it up to a compilable state, and then finish anything left
to go on it.
I think it will be tested and good to go for 2022.3.
|
@XLTechie any chance you can continue this any time soon? |
This comment was marked as outdated.
This comment was marked as outdated.
5fb12ae
to
cb0466e
Compare
See test results for failed build of commit 054795cbe5 |
This comment was marked as outdated.
This comment was marked as outdated.
For issues with compile setup, feel free to ask on nvda-devel mailing list where such issues are usually discussed and addressed. |
65efc5c
to
becd99a
Compare
See test results for failed build of commit b7653daab8 |
@XLTechie - do you plan to finish this work? Otherwise I think it should be closed |
@seanbudd yes. I put it aside because I kept running into wx issues with text formatting being very strange. I'll look at it again, and if I can't make it work as-is, I'll split it into separate PRs addressing the major portions, so the important bits can get merged.
Sorry for letting it lay for so long--time flies.
|
No problem - draft PRs are totally fine - we just want to make sure theyre not fully abandoned |
gui.onRunCOMRegistrationFixesCommand: - No longer shows success dialog on failure, or when the UAC is canceled or declined (nvaccess#12345).. - We now catch the Windows error that signals user cancel of UAC, and return as if "NO" had been initially chosen. - If there is a Windows error other than cancel of UAC, alert the user and show the error in a dialog. - Rewrote initial dialog message to be more friendly and helpful, and removed warning icon (nvaccess#12351). - Switched from using YES and NO buttons, to OK and Cancel (CANCEL button provides visual closure and escape key use). - Added a docstring and fully linted code. Added more debug logging.
becd99a
to
239810d
Compare
a37cbb5
to
5dfea2a
Compare
Co-authored-by: Sascha Cowley <[email protected]>
@SaschaCowley I have addressed your latest review. I'm not sure I like the user guide reordered as you requested, but I do agree with your reason for wanting to do it. In the end, all of the same information is there, which ever order it is presented in, so I'm fine with whatever. |
@XLTechie I agree it really doesn't read very well now. Perhaps we could rewrite it to be a little less technical and more to the point of what users are likely to care about? What do you think of something like this? Installing and uninstalling programs on a computer can sometimes cause problems with the Windows registry that result in NVDA behaving abnormally.
This can happen, for example, after installing and uninstalling Adobe Reader, Math Player and other programs.
It can also happen after Windows updates, or during other events that access the registry.
THE COM Registration Fixing Tool attempts to fix these issues by repairing accessibility entries in the registry.
The types of issues this tool can fix include:
* NVDA reporting "unknown" or "pane" when navigating in browsers such as Firefox or Edge, mail programs such as Thunderbird, Windows Explorer, the task bar, and other programs.
* NVDA failing to switch between focus mode and browse mode when you expect it to.
* NVDA being very slow when navigating in browsers while using browse mode.
Because this tool corrects entries in the Windows registry, it requires administrative access to work, just like when installing a program.
If you have UAC (User Access Control) enabled, as most users do, you will need to follow whatever prompts are presented by UAC to run the tool successfully. |
…y be used instead. This reverts commit 78a1398.
@SaschaCowley How about this? Not quite what you wrote, but closer. @Qchristensen you might want to get in on this user guide discussion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated user guide and dialog intro text reads well. Great work everyone
Link to issue number:
Fixes #10799
Fixes #12345
Fixes #12351
Replaces #12349
Summary of the issue:
Escape
orAlt+F4
keys (Run COM Registration fixing tool Dialog can't be closed by ALT+F4 or ESC #10799).User facing changes:
Escape
/Alt+F4
to leave the dialog, as well as hittingCancel
.F1
context help is now available.Development details:
gui.nvdaControls._ContinueCancelDialog
.Testing strategy:
Known issues with pull request:
gui.postPopup
is supposed to fix this, but it doesn't.Code Review Checklist:
Summary by CodeRabbit
New Features
User Experience Improvements
escape
key oralt+f4
.